Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0140

reference: 182-tree-1
name: 0140
tree-preservation-order: undefined
182-tpo-1
uprn
address-text
point: POINT (-0.938481 50.865435)
geometry: MULTIPOLYGON (((-0.938368 50.865423,-0.938373 50.865445,-0.938388 50.865466,-0.938413 50.865482,-0.938445 50.865492,-0.938480 50.865496,-0.938515 50.865493,-0.938547 50.865483,-0.938572 50.865467,-0.938589 50.865447,-0.938595 50.865425,-0.938590 50.865403,-0.938574 50.865383,-0.938549 50.865367,-0.938518 50.865356,-0.938483 50.865352,-0.938448 50.865355,-0.938416 50.865365,-0.938390 50.865381,-0.938374 50.865401,-0.938368 50.865423)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL